Skip to content

feat: add hyperpod-resource-ownership and hyperpod-compute-configuration subcharts, disabled by default - #485

Merged
papriwal merged 1 commit into
aws:mainfrom
meghanajs99:release-ro-cc
Nov 22, 2026
Merged

papriwal merged 1 commit into
aws:mainfrom
meghanajs99:release-ro-cc

Conversation

@meghanajs99

@meghanajs99 meghanajs99 commented Nov 22, 2026 •

Copy link
Copy Markdown
Contributor

What's changing and why?

Adds two HyperPod components to the HyperPod Helm chart as subcharts, both disabled by default:

  • hyperpod-resource-ownership: records who created each RayJob, HyperPodPyTorchJob, InferenceEndpointConfig and JumpStartModel, and lets only the creator, the operators and cluster admins update or delete the ones marked OwnerOnly. A mutating webhook records the creator; ValidatingAdmissionPolicies enforce OwnerOnly, including status and scale writes.
  • hyperpod-compute-configuration: the ComputeConfiguration CRD and its admission webhook. An admin defines named compute shapes in a namespace; a RayJob, HyperPodPyTorchJob or InferenceEndpointConfig that references one (label compute.configuration.sagemaker.amazonaws.com/name) gets its compute filled in and checked. Namespaces labelled compute.configuration.sagemaker.amazonaws.com/enforcement=enabled require every such workload to use one.

Both webhook images come from the regional HyperPod ECR repository for the 14 supported Regions (region, then global.region), by tag (defaults: resource ownership 1.0.20.0_1.0.3.0, compute configuration 1.0.26.0_1.0.5.0) or by digest. Both need cert-manager and Kubernetes 1.30+.

Changes:

  • charts/hyperpod-resource-ownership/ and charts/hyperpod-compute-configuration/: the subcharts.
  • HyperPodHelmChart/Chart.yaml: two file:// dependencies with condition: <name>.enabled.
  • HyperPodHelmChart/values.yaml: enabled: false blocks for both.
  • helm_chart/readme.md: two rows in the components table.

main's hyperpod-kubernetes-resource-monitor entries in the parent Chart.yaml, values.yaml and readme.md are unchanged; the new entries follow them. Nothing else in main changes (0 deleted lines).

Before/After UX

Before: the HyperPod Helm chart has neither component.

After: default install: no change; neither subchart renders any objects. Opt in:

helm upgrade --install dependencies HyperPodHelmChart --namespace kube-system \
  --set cert-manager.enabled=true \
  --set hyperpod-resource-ownership.enabled=true \
  --set hyperpod-compute-configuration.enabled=true \
  --set global.region=<region>

How was this change tested?

  • helm dependency update + helm lint HyperPodHelmChart: 0 failed, with both subcharts off and on.
  • helm template (default): no objects from either subchart; hyperpod-kubernetes-resource-monitor still on by default; hyperpod-inference-operator still 2.8.3.
  • helm template with both enabled renders each Region's account and the default tags; both images exist in all 14 Regions' ECR repositories (compute configuration 1.0.26.0_1.0.5.0: sha256:1f4b89be…57d4; resource ownership 1.0.20.0_1.0.3.0: sha256:2adcad86…f57a).
  • Both subcharts were installed on live HyperPod EKS clusters and covered by their integration test suites and canaries. The compute configuration subchart at this version was installed on a HyperPod cluster with task governance (Kueue) and checked with real workloads: Kueue admitting, evicting and readmitting RayJobs in an enforced namespace, the CRD's validation (41 cases), and the disruption budget.

Are unit tests added?

No; this adds Helm subcharts. The webhooks and policies are tested in their own packages.

Are integration tests added?

Not in this repository; each component's integration tests run against live clusters in its pipeline.

@meghanajs99
meghanajs99 requested a review from a team as a code owner November 22, 2026 01:15
@meghanajs99
meghanajs99 deployed to manual-approval November 22, 2026 01:15 — with GitHub Actions Active
…ion subcharts, disabled by default

hyperpod-resource-ownership records who created each RayJob, HyperPodPyTorchJob,
InferenceEndpointConfig and JumpStartModel (the created-by annotation) and lets only the
creator, the operators and cluster admins update or delete the ones marked OwnerOnly,
including through their status and scale subresources. The owner can change
ownership-type; created-by is immutable.

hyperpod-compute-configuration installs the ComputeConfiguration CRD and its admission
webhook. An admin defines named compute shapes in a namespace; a RayJob,
HyperPodPyTorchJob or InferenceEndpointConfig that references one by label gets its
compute filled in and checked, and namespaces labelled
compute.configuration.sagemaker.amazonaws.com/enforcement=enabled require every such
workload to use one.

Both webhook images come from the regional HyperPod ECR repository for the 14 supported
Regions, by tag or by digest; an image override must be pinned by digest. Both require
cert-manager and Kubernetes 1.30+.

@HariniNarayanan HariniNarayanan left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@papriwal
papriwal merged commit b063e88 into aws:main Nov 22, 2026
5 of 6 checks passed

This branch was successfully deployed

1 active deployment
manual-approval — 7a0b3ba8 Deployed Nov 22, 2026 by meghanajs99 via wait-for-approval #854
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants